Systems for requesting and/or transmitting user data within resource transfer event messaging

ABSTRACT

Configuring resource transfer event messages to include, not only the user data required to affect the resource transfer (e.g., resource repository identifier and the like), but other user data related to the resource transfer event, such as user preference data. The resource transfer event messages are communicated to resource storage entities that subsequently store user records that associate users with the resource transfer events and the additional user data. In this regard, a security benefit is realized, in that, resource storage entities can leverage the additional data to investigate potential nefarious actions. Moreover, by including the additional user information in resource transfer event messages communicated to resource storage entities, the volume of resource transfer event messages or other network-based messages is lessened thereby limiting network traffic and making the overall process more efficient and effective.

FIELD OF THE INVENTION

The present invention is generally directed to resource transfer eventsand, more specifically, systems, methods, computer program products andthe like that request and/or transmit other user data, besides resourceaccount identifier data, within resource transfer event messaging.

BACKGROUND

The data that is included in resource transfer event messagescommunicated to resource storage entities is typically limited toidentifying the resource provider and their respective resource accountidentifier data. However, resource storage entities as well as theparties conducting the resource transfer event would benefit from havingthe resource storage entities being able to associate other user datarelated to the resource transfer event with the user.

Moreover, at any moment in time the volume of resource transfer eventsoccurring is enormous, which means that the volume of messages beingcommunicated to conduct such resource transfer events places a burden onthe resource transfer event processing networks communicating suchmessages.

Therefore, a need exists to develop systems, methods, and computerprogram products and like that provide for the resource storage entityto have access to other user data associated with resource transferevents. Further, the desired systems, methods, and computer programproducts and like should lessen the volume of messaging occurring on theresource transfer event processing networks, thereby lessening theburden placed on the networks and limiting the likelihood of delaysand/or down-times.

BRIEF SUMMARY

The following presents a simplified summary of one or more embodimentsof the invention in order to provide a basic understanding of suchembodiments. This summary is not an extensive overview of allcontemplated embodiments and is intended to neither identify key orcritical elements of all embodiments, nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

Embodiments of the present invention address the above needs and/orachieve other advantages by providing systems, methods, computer programproducts and/or the like for configuring resource transfer eventmessages to include, not only the user data required to affect theresource transfer (e.g., resource repository identifier and the like),but other user data related to the resource transfer event. The otheruser data may include, but is not limited to, user configurationpreference data, such as preferences (e.g., sizes, colors and the like)for the object or service being acquired, a geographic locationpreference for delivery of the object or performance of the service, acontact preference (e.g., email address, telephone number or the like)for corresponding with the resource provider and the like.

The resource transfer event messages are communicated to the resourcestorage entity that is associated with the resource transfer event andstores the resource provider's resource repository. In this regard, theresource storage entity provides for a database or other storagemechanism that stores the user records that associate the resourceprovider with the resource transfer event and include the other userdata related to the resource transfer event.

In specific embodiments of the invention, once the resource storageentity has received the resource transfer event message and the eventhas been validated, the resource storage entity communicates a secondresource transfer event message to the resource recipient that includesthe additional user data. In this regard, the present invention may, inspecific embodiments of the invention, prevent from having tocommunicate a direct message from the resource provider or the resourcetransfer event entry platform that includes the additional user data.

In specific embodiments of the invention, the messaging is implementedin conjunction with a real-time processing network configured tocomplete (i.e., distribute and settle resources) the resource transferevent in real-time or near real-time to the initiation of the resourcetransfer event. In such embodiments of the invention, resource transferevent requests may be communicated from the resource recipient to theresource provider that are configured to include requests for theadditional user data (e.g., requests for the object/service preferences,the geographic location preference for delivering the object orperforming the service and the like). In response to receiving theresource transfer event request message, the resource providercommunicates a resource transfer event message that is configured toprovide for the requested additional user data. In such embodiments ofthe invention, the resource transfer event message or the resourcetransfer event request message may have designated fields for theadditional user data or requests or the data or requests may be codedwithin specific fields of an alphanumeric coded included in anunstructured remittance filed or the like.

In other specific embodiments of the invention, the resource transferevent message is implemented in conjunction with conventionalnetwork-based resource transfer event processing, such resource transferevents initiated at network sites or the like.

A system for resource transfer event messaging defines first embodimentsof the invention. The system includes a first computing platform havinga first memory and at least one first processor in communication withthe first memory. The first memory stores first instructions that areexecutable by the at least one first processor. The instructions areconfigured to receive inputs that define (i) first user data associatedwith a resource provider and required to affect a resource transferevent conducted between the resource provider and a resource recipient,and (ii) second user data associated with the resource provider that isdata other than the first user data. In addition, the instructions areconfigured to generate a resource transfer event message including (i)the first user data, and (ii) the second user data, and communicate theresource transfer event message to a resource storage entity associatedwith the first user.

The system additionally includes a second computing platform having asecond memory and at least one second processor in communication withthe second memory. The second memory stores second instructions that areexecutable by the at least one second processor. The second instructionsare configured to receive, at the resource storage entity, the resourcetransfer event message, validate the resource transfer event based onthe first user data, and store a user record that associates theresource provider with the resource transfer event and the second userdata.

In specific embodiments of the system, the second instructions arefurther configured to, in response to validating the resource transferevent, generate a second resource transfer event message including thesecond user data and less than an entirety of the first user data, andcommunicate the second resource transfer event message to the resourcerecipient. In specific embodiments of the system, the resource recipientdoes not receive any other messages associated with the resourcetransfer event.

The further specific embodiments of system, the second user dataincludes user preference data comprising at least one selected from thegroup consisting of (i) an object or service preference, (ii) a physicallocation preference for conveying the object or performing the service,and (iii) a contact preference for communicating with the resourceprovider. In further embodiments of the system, the first instructionsconfigured to receive the inputs are further configured to receive theinputs from one of (i) the resource recipient, or (ii) the resourcestorage entity.

In other specific embodiments of the system, the first instructions areimplemented in conjunction with a real-time processing networkconfigured to process the resource transfer event in real-time. In suchembodiments of the system, the resource transfer event message isfurther defined as a real-time processing messaging. In relatedembodiments of the system, the first instructions are further configuredto generate a resource transfer event request message that iscommunicated to the resource provider and is configured to request (i)the resource transfer event and (ii) the second user data. In suchembodiments of the system, the first instructions configured to receivethe inputs are further configured to receive the inputs from theresource provider in response to receiving the resource transfer eventrequest message. In other related embodiments of the system, the firstinstructions configured to generate the resource transfer event requestmessage are further configured to receive inputs from the resourcerecipient that define the second user data that is being requested.

In further related embodiments of the system, the first instructionsconfigured to generate the resource transfer event message or theresource transfer event request message are further configured toprovide the second user data as an alphanumeric code within a designatedfield of the resource transfer event message or the resource transferevent request message. Predetermined characters in the alphanumeric codecorrespond to different second user datum or different requests forsecond user datum.

A computer-implemented method for resource transfer event messagingdefines second embodiments of the invention. The method is executed byone or more computing processor devices. The method includes receivinginputs that define (i) first user data associated with a resourceprovider and required to affect a resource transfer event conductedbetween the resource provider and a resource recipient, and (ii) seconduser data associated with the resource provider that is data other thanthe first user data. In addition, the method includes generating aresource transfer event message including (i) the first user data, and(ii) the second user data and communicating the resource transfer eventmessage to a resource storage entity associated with the first user.Moreover, the method includes validating, at the resource storageentity, the resource transfer event based on the first user data andstoring a user record that associates the resource provider with theresource transfer event and the second user data.

In specific embodiments the computer-implemented method furtherincludes, in response to validating the resource transfer event message,generating a second resource transfer event message including the seconduser data and less than an entirety of the first user data, andcommunicating the second resource transfer event message to the resourcerecipient. In specific embodiments of the method, the resource recipientdoes not receive any other messages associated with the resourcetransfer event.

In other specific embodiments of the computer-implemented method, thesecond user data includes user preference data comprising at least oneselected from the group consisting of (i) an object or servicepreference, (ii) a physical location preference for conveying the objector performing the service, and (iii) a contact preference forcommunicating with the resource provider.

In still further specific embodiments of the computer-implementedmethod, receiving the inputs further comprises receiving the inputs fromone of (i) the resource recipient, or (ii) the resource storage entity.

Moreover, in additional specific embodiments the computer-implementedmethod is implemented in conjunction with a real-time processing networkconfigured to process the resource transfer event in real-time and theresource transfer event message is further defined as a real-timeprocessing messaging. In such embodiments the computer-implementedmethod may further include generating a resource transfer event requestmessage that is communicated to the resource provider and is configuredto request (i) the resource transfer event and (ii) the second userdata.

A computer program product including a non-transitory computer-readablemedium defines third embodiments of the invention. The computer-readablemedium includes a first set of codes for causing a computer to receiveinputs that define (i) first user data associated with a resourceprovider and required to affect a resource transfer event conductedbetween the resource provider and a resource recipient, and (ii) seconduser data associated with the resource provider, wherein the second userdata is data other than the first user data. Further, thecomputer-readable medium includes a second set of codes for causing acomputer to generate a resource transfer event message including (i) thefirst user data, and (ii) the second user data and a third set of codesfor causing a computer to communicate the resource transfer eventmessage to a resource storage entity associated with the first user.Moreover, the computer-readable medium includes a fourth set of codesfor causing a computer to validate, at the resource storage entity, theresource transfer event based on the first user data, and a fifth set ofcodes for causing a computer to store a user record that associates theresource provider with the resource transfer event and the second userdata.

In additional embodiments of the computer program product, thecomputer-readable medium further includes a sixth set of codes forcausing a computer to, in response to validating the resource transferevent message, generate a second resource transfer event messageincluding the second user data and less than an entirety of the firstuser data, and a seventh set of codes for causing a computer tocommunicate the second resource transfer event message to the resourcerecipient. In specific embodiments of the computer program product, theresource recipient does not receive any other messages associated withthe resource transfer event.

In specific embodiments of the computer program product, the second userdata includes user preference data comprising at least one selected fromthe group consisting of (i) an object or service preference, (ii) aphysical location preference for conveying the object or performing theservice, and (iii) a contact preference for communicating with theresource provider.

In other specific embodiments of the computer program product the setsof codes are implemented in conjunction with a real-time processingnetwork configured to process the resource transfer event in real-timeand the resource transfer event message is further defined as areal-time processing messaging. In related embodiments of the computerprogram product, the computer-readable medium further includes a sixthset of codes for causing a computer to generate a resource transferevent request message that is communicated to the resource provider andis configured to request (i) the resource transfer event and (ii) thesecond user data.

Thus, according to embodiments of the invention, which will be discussedin greater detail below, the present invention provides configuringresource transfer event messages to include, not only the user datarequired to affect the resource transfer (e.g., resource repositoryidentifier and the like), but other user data related to the resourcetransfer event, such as user preference data and the like. The resourcetransfer event messages are communicated to resource storage entitiesthat subsequently store user records that associate users with theresource transfer events and the additional user data. In this regard,the resource storage entities can leverage the additional data toinvestigate potential nefarious actions, confirm resource storage eventpreferences/specifics and the like. Moreover, the present invention, inspecific embodiments lessens the volume of resource transfer eventmessages or other network-based messages thereby limiting networktraffic and making the overall process more efficient and effective.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the disclosure in general terms,reference will now be made to the accompanying drawings, wherein:

FIG. 1 is a schematic/block diagram of a system for generating andcommunicating resource transfer messages including other user databesides the user′ resource transfer event credentials, in accordancewith embodiments of the present invention;

FIG. 2 is a schematic/block diagram of a system for leveraging otheruser data in resource transfer event messages, such as preference data,to customize/personalize a user browsing experience; in accordance withembodiments of the present invention;

FIG. 3 is a block diagram depicting exemplary resource transfer eventmessages used in conjunction with a real-time processing network; inaccordance with embodiments of the present invention;

FIG. 4 is a schematic diagram of a system for processing resourcetransfer events in a real-time processing network, in accordance withsome embodiments of the present disclosure;

FIG. 5 is a schematic diagram of a system for processing resources eventin a real-time processing network using a clearing house system, inaccordance with embodiments of the present invention;

FIG. 6 is a schematic diagram of a system for processing financialtransactions/disbursements in a real-time processing network, inaccordance with embodiments of the present invention;

FIG. 7 is a schematic diagram of a system for processing financialtransactions/disbursements in a real-time processing network using aclearing house system, in accordance with embodiments of the presentinvention;

FIG. 8 is a flow diagram of a method for resource transfer eventmessaging, in accordance with embodiments of the present invention; and

FIG. 9 is a flow diagram of a method for leveraging use of userpreference data in resource transfer event messages to customize,personalize and/or refine user experiences at web sites, in accordancewith embodiments of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like numbers refer to like elements throughout.

As will be appreciated by one of skill in the art in view of thisdisclosure, the present invention may be embodied as a system, a method,a computer program product or a combination of the foregoing.Accordingly, embodiments of the present invention may take the form ofan entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.), or anembodiment combining software and hardware aspects that may generally bereferred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program productcomprising a computer-usable storage medium having computer-usableprogram code/computer-readable instructions embodied in the medium.

Any suitable computer-usable or computer-readable medium may beutilized. The computer usable or computer-readable medium may be, forexample but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, ordevice. More specific examples (e.g., a non-exhaustive list) of thecomputer-readable medium would include the following: an electricalconnection having one or more wires; a tangible medium such as aportable computer diskette, a hard disk, a time-dependent access memory(RAM), a read-only memory (ROM), an erasable programmable read-onlymemory (EPROM or Flash memory), a compact disc read-only memory(CD-ROM), or other tangible optical or magnetic storage device.

Computer program code/computer-readable instructions for carrying outoperations of embodiments of the present invention may be written in anobject oriented, scripted or unscripted programming language such asJAVA, PERL, SMALLTALK, C++, PYTHON or the like. However, the computerprogram code/computer-readable instructions for carrying out operationsof the invention may also be written in conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages.

Embodiments of the present invention are described below with referenceto flowchart illustrations and/or block diagrams of methods or systems.It will be understood that each block of the flowchart illustrationsand/or block diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce aparticular machine, such that the instructions, which execute by theprocessor of the computer or other programmable data processingapparatus, create mechanisms for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instructions, whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational events to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions, which execute on the computer or other programmableapparatus, provide events for implementing the functions/acts specifiedin the flowchart and/or block diagram block or blocks. Alternatively,computer program implemented events or acts may be combined withoperator or human implemented events or acts in order to carry out anembodiment of the invention.

As the phrase is used herein, a processor may be “configured to” performor “configured for” performing a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing particular computer-executable programcode embodied in computer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

Thus, systems, apparatus, and methods are described in detail below forconfiguring resource transfer event messages to include, not only theuser data required to affect the resource transfer (e.g., resourcerepository identifier and the like), but other user data related to theresource transfer event. For example, in those embodiments of theinvention in which the resource transfer event is a payment transactionrelated to acquisition of a product or service, the resource transferevent messages are payment messages and the other user data is any otherdata other than data affects the payment (e.g., payment accountidentifier data).

The other user data may include, but is not limited to, user preferencedata, such as preferences (e.g., sizes, colors and the like) for theobject or service being acquired, a geographic location preference fordelivery of the object or performance of the service, a contactpreference (e.g., email address, telephone number or the like) forcorresponding with the resource provider and the like.

The resource transfer event messages are communicated to the resourcestorage entity that is associated with the resource transfer event andstores the resource provider's resource repository. For example, inthose embodiments of the invention in which the resource transfer eventis a payment transaction, the payment messages are communicated to thepayment entity, such as financial institution at which the payor'spayment account is held. The resource storage entity provides for adatabase or other storage mechanism that stores the user records thatassociate the resource provider with the resource transfer event andinclude the other user data related to the resource transfer event. Morespecifically, the payment entity, such as a financial institution or thelike, stores user records that associate the payor with the paymenttransaction and includes the other user data communicated in the paymentmessage.

In specific embodiments of the invention, once the resource storageentity has received the resource transfer event message and the eventhas been validated, the resource storage entity communicates a secondresource transfer event message to the resource recipient that includesthe additional user data. For example, in those embodiments of theinvention in which the resource transfer event is a payment transaction,once the payment entity has received the payment message and thetransaction has been validated, the payment entity communicated anotherpayment-related message to the payee that includes necessary paymentinformation and the other user data. In this regard, the presentinvention may, in specific embodiments of the invention, prevent fromhaving to communicate a direct message from the resource provider, suchas a payee, or the resource transfer event entry platform (e.g.,e-commerce site or real-time payment platform) that includes theadditional user data.

In specific embodiments of the invention, the messaging is implementedin conjunction with a real-time processing network configured tocomplete (i.e., distribute and settle resources) the resource transferevent in real-time or near real-time to the initiation of the resourcetransfer event. For example, in those embodiments of the invention inwhich the resource transfer event is a payment transaction, themessaging is implemented in conjunction with a real-time payment networkconfigured to complete payment transaction (i.e., distribute/settlepayment) in real-time or near real-time to the initiation of the paymentevent.

In such embodiments of the invention, resource transfer event requestsmay be communicated from the resource recipient to the resource providerthat are configured to include requests for the additional user data(e.g., requests for the object/service preferences, the geographiclocation preference for delivering the object or performing the serviceand the like). For example, in those embodiments of the invention inwhich the resource transfer event is a payment transaction, real-timepayment requests may be communicated from the payee to the payor thatare configured to include requests for specific additional user data,such as user preference data. In response to receiving the resourcetransfer event request message, the resource provider communicates aresource transfer event message that is configured to provide for therequested additional user data. For example, in specific embodiments ofthe invention, in response to receiving the real-time payment request,the payor communicates a real-time payment message that includes therequested other user data. In such embodiments of the invention, theresource transfer event message or the resource transfer event requestmessage may have designated fields for the additional userdata/requests, or the data/requests may be coded within specific fieldsof an alphanumeric coded included in an unstructured remittance filed orthe like.

In other specific embodiments of the invention, the resource transferevent message is implemented in conjunction with conventionalnetwork-based resource transfer event processing, such resource transferevents initiated at network sites or the like.

Referring to FIG. 1, a system 2 for resource transfer event messaging ispresented, in accordance with embodiments of the present invention. Thesystem is implemented in a distributed communication network 4, whichmay comprise one or more of the Internet, intranet(s), cellularnetwork(s) or the like. The system 2 includes a first computing platform6 having a first memory 8 and one or more first processing devices 10 incommunication with the first memory 8. First computing platform 6 may bepart of a resource event processing platform/network or part of areal-time resource transfer event processing platform/network.

First computing platform 6 may comprise one or more server devices orthe apparatus may comprise one of the one or more other computingdevices (e.g., mainframes, storage devices, personal computers (PCs) orthe like) capable of executing computer-readable instructions, such asalgorithms, modules, routines, applications and the like. First memory 8may comprise volatile and non-volatile memory, such as read-only and/orrandom-access memory (RAM and ROM), EPROM, EEPROM, flash cards, or anymemory common to computer platforms). Moreover, first memory 8 maycomprise cloud storage, such as provided by a cloud storage serviceand/or a cloud connection service.

First processing device(s) 10 may be an application-specific integratedcircuit (“ASIC”), or other chipset, logic circuit, or other dataprocessing device. First processing device 8 may execute an applicationprogramming interface (“API”) (not shown in FIG. 1) that interfaces withany resident instructions, such as first instructions 12 andsub-instructions associated therewith or the like stored in the firstmemory 8 of the first computing platform 6. First processing device 10may include various processing subsystems (not shown in FIG. 1) embodiedin hardware, firmware, software, and combinations thereof, that enablethe functionality of first computing platform 6 and the operability ofthe first computing platform 6 on a distributed computing network 4. Forexample, processing subsystems allow for initiating and maintainingcommunications and exchanging data with other networked devices. For thedisclosed aspects, processing subsystems of first processing device(s)10 may include any subsystem used in conjunction with first instructions12 and related sub-instructions, sub-routines, algorithms,sub-algorithms, modules, sub-modules thereof.

First computer platform 6 may additionally include a communicationsmodule (not shown in FIG. 1) embodied in hardware, firmware, software,and combinations thereof, that enables electronic communications betweenthe first computing platform 6 and other networks, such as real-timeprocessing network 300 (shown in FIGS. 4-7) and devices. Thus,communication module may include the requisite hardware, firmware,software and/or combinations thereof for establishing and maintaining anetwork communication connection.

First memory 8 stores first instructions 12 that are executable by atleast one of the first processing device(s) 10 and are configured togenerate and communicate a resource transfer event message 22 to aresource storage entity. In specific embodiments of the invention inwhich the resource transfer event message 22 is a payment message, thepayment message is communicated to payment processing entity, such afinancial institution or the like.

First instructions 12 are configured to receive inputs 13 that define(i) first user data 14 associated with the resource provider andrequired to affect a resource transfer event between a resourcerecipient and the resource provider. In specific embodiments of theinvention, first user data 14 includes resource transfer eventcredentials 16, such as payment account identifier or the like.Additionally, inputs 13 define (ii) second user data 18 that isassociated with the resource provider and is data other than the firstuser data 14. In specific embodiments of the system, second user data 18includes user/resource provider preference data 20. For example, inthose embodiments of the invention in which the resource transfer eventis a payment event, the user/resource provider preference data mayinclude, but is not limited to, object/service configuration preferencedata (e.g., size, color or the like), geographical location preferencedata indicating a delivery or performance location, contact preferencedata (e.g., email address, telephone number or the like). In specificembodiments of the invention the some or all of the inputs 13 may bereceived from one or more of the resource recipient, the resourcestorage entity, a web site, a web browser or the like.

First instructions 12 are further configured to generate a resourcetransfer event message 22 that includes the first data 14 and the seconddata 18 and communicate the message 22 to a resource storage entityassociated with the resource provider. In specific embodiments of theinvention, in which the resource transfer event is a payment event, thepayment message is communicated to a payment processing entity, such asa financial institution or the like.

System 2 additionally includes a second computing platform 24 having asecond memory 26 and one or more second processing devices 28 incommunication with the second memory 28. Second computing platform 24 ispart of a resource transfer event processing platform/network and, thusmay be executed by a resource storage entity, such as a paymentprocessing entity, e.g., a financial institution or the like.

Second computing platform 24 may comprise one or more server devices orthe apparatus may comprise one of the one or more other computingdevices (e.g., mainframes, storage devices, personal computers (PCs) orthe like) capable of executing computer-readable instructions, such asalgorithms, modules, routines, applications and the like. Second memory26 may comprise volatile and non-volatile memory, such as read-onlyand/or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards,or any memory common to computer platforms). Moreover, second memory 26may comprise cloud storage, such as provided by a cloud storage serviceand/or a cloud connection service.

Second processing device(s) 28 may be an application-specific integratedcircuit (“ASIC”), or other chipset, logic circuit, or other dataprocessing device. Second processing device 28 may execute anapplication programming interface (“API”) (not shown in FIG. 1) thatinterfaces with any resident instructions, such as second instructions30 and sub-instructions associated therewith or the like stored in thesecond memory 26 of the second computing platform 24. Second processingdevice 28 may include various processing subsystems (not shown inFIG. 1) embodied in hardware, firmware, software, and combinationsthereof, that enable the functionality of second computing platform 24and the operability of the second computing platform 24 on a distributedcomputing network 4. For example, processing subsystems allow forinitiating and maintaining communications and exchanging data with othernetworked devices. For the disclosed aspects, processing subsystems ofsecond processing device(s) 28 may include any subsystem used inconjunction with second instructions 30 and related sub-instructions,sub-routines, algorithms, sub-algorithms, modules, sub-modules thereof.

Second computer platform 24 may additionally include a communicationsmodule (not shown in FIG. 1) embodied in hardware, firmware, software,and combinations thereof, that enables electronic communications betweenthe second computing platform 24 and other networks, such as real-timeprocessing network 300 (shown in FIGS. 4-7) and devices. Thus,communication module may include the requisite hardware, firmware,software and/or combinations thereof for establishing and maintaining anetwork communication connection.

Second memory 26 stores second instructions 30 that are executable by atleast one of the second processing device(s) 28 and are configured toreceive the resource transfer event message 22 and perform resourcetransfer event validation resource 32 based on the first user data 14.Resource transfer event validation 32 may include, but is not limitedto, verifying (i) the resource transfer event credentials 16, (ii)available resources in the corresponding resource repository and thelike. In addition, second instructions 22 are configured to store a userrecord 34 that associates the resource provider with the resourcetransfer event and the second user data.

Referring to FIG. 2, a system 40 for leveraging user data, specificallyuser preference data, included in resource transfer event messages forcustomizing/personalizing and/or refining a user's web browsingexperience. The system is implemented in a distributed communicationnetwork 4, which may comprise one or more of the Internet, intranet(s),cellular network(s) or the like. The system 40 includes a firstcomputing platform 42 having a first memory 44 and one or more firstprocessing devices 46 in communication with the first memory 44. Firstcomputing platform 44 may be part of or in control of by a resourcestorage entity, such as a payment processing entity, e.g., a financialinstitution or the like.

First computing platform 42 may comprise one or more server devices orthe apparatus may comprise one of the one or more other computingdevices (e.g., mainframes, storage devices, personal computers (PCs) orthe like) capable of executing computer-readable instructions, such asalgorithms, modules, routines, applications and the like. First memory44 may comprise volatile and non-volatile memory, such as read-onlyand/or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards,or any memory common to computer platforms). Moreover, first memory 44may comprise cloud storage, such as provided by a cloud storage serviceand/or a cloud connection service.

First processing device(s) 46 may be an application-specific integratedcircuit (“ASIC”), or other chipset, logic circuit, or other dataprocessing device. First processing device 46 may execute an applicationprogramming interface (“API”) (not shown in FIG. 2) that interfaces withany resident instructions, such as user database 48 and sub-instructionsassociated therewith or the like stored in the first memory 44 of thefirst computing platform 42. First processing device 46 may includevarious processing subsystems (not shown in FIG. 2) embodied inhardware, firmware, software, and combinations thereof, that enable thefunctionality of first computing platform 42 and the operability of thefirst computing platform 42 on a distributed computing network 4. Forexample, processing subsystems allow for initiating and maintainingcommunications and exchanging data with other networked devices. For thedisclosed aspects, processing subsystems of first processing device(s)46 may include any subsystem used in conjunction with user database 48and related sub-instructions, sub-routines, algorithms, sub-algorithms,modules, sub-modules thereof.

First computer platform 42 may additionally include a communicationsmodule (not shown in FIG. 2) embodied in hardware, firmware, software,and combinations thereof, that enables electronic communications betweenthe first computing platform 42 and other networks, such as real-timeprocessing network 300 (shown in FIGS. 4-7) and devices. Thus,communication module may include the requisite hardware, firmware,software and/or combinations thereof for establishing and maintaining anetwork communication connection.

First memory 44 stores user database 48 that is executable by at leastone of the first processing device(s) 46 and are configured to storeuser data 52 for a plurality of users 50. The user data 52 associateseach of the users 50 with user preference data 54 that has been receivedvia a resource transfer event message 22 communicated to a resourcestorage entity during resource transfer events. The user preference dataincludes, but is not limited to, object/service configuration preferencedata (e.g., size, color or the like) related to objects/products and/orservices acquired in previous resource transfer events.

System 40 additionally includes a second computing platform 58 having asecond memory 60 and one or more second processing devices 62 incommunication with the second memory 60. Second memory 60 storesinstructions 64 that are executable by at least one of the secondprocessing device(s) 62 and may be implemented in conjunction with aresource storage entity portal, such as a financial institution portalor any other application that provides network access or the like.

Second computing platform 58 may comprise one or more server devices orthe apparatus may comprise one of the one or more other computingdevices (e.g., mainframes, storage devices, personal computers (PCs) orthe like) capable of executing computer-readable instructions, such asalgorithms, modules, routines, applications and the like. Second memory60 may comprise volatile and non-volatile memory, such as read-onlyand/or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards,or any memory common to computer platforms). Moreover, second memory 60may comprise cloud storage, such as provided by a cloud storage serviceand/or a cloud connection service.

Second processing device(s) 62 may be an application-specific integratedcircuit (“ASIC”), or other chipset, logic circuit, or other dataprocessing device. Second processing device 62 may execute anapplication programming interface (“API”) (not shown in FIG. 2) thatinterfaces with any resident instructions, such as instructions 64 andsub-instructions associated therewith or the like stored in the secondmemory 60 of the second computing platform 58. Second processing device62 may include various processing subsystems (not shown in FIG. 2)embodied in hardware, firmware, software, and combinations thereof, thatenable the functionality of second computing platform 58 and theoperability of the second computing platform 58 on a distributedcomputing network 4. For example, processing subsystems allow forinitiating and maintaining communications and exchanging data with othernetworked devices. For the disclosed aspects, processing subsystems ofsecond processing device(s) 62 may include any subsystem used inconjunction with instructions 64 and related sub-instructions,sub-routines, algorithms, sub-algorithms, modules, sub-modules thereof.

Second computer platform 58 may additionally include a communicationsmodule (not shown in FIG. 2) embodied in hardware, firmware, software,and combinations thereof, that enables electronic communications betweenthe second computing platform 58 and other networks, such as real-timeprocessing network 300 (shown in FIGS. 4-7) and devices. Thus,communication module may include the requisite hardware, firmware,software and/or combinations thereof for establishing and maintaining anetwork communication connection.

Instructions 64 are configured to receive authentication credentials 66from one of the users 50 and, in response perform user authentication 68by comparing the received authentication credentials 66 toauthentication credentials 70 stored by the resource storage entity. Inresponse to authenticating the user, instructions 64 are configured toprovide the user access 72 a network 74 configured for performingresource transfer events.

In response to the user navigating to a network site 76 within network74, instructions 64 are configured to access the user database 48 toretrieve the user preference 54, specifically object/serviceconfiguration data 56. Moreover, instructions 64 are configured tocustomize/personalize the content provided to the user while browsingthe network site 76 based on the user preference data 54 associated withthe user 50. In this regard, according to specific embodiments of theinvention, instructions 64 implement user preference data 54 fromprevious resource transfer events to determine which content to presentto the user as they browse the network site 76. For example, the contentmay be of a preferred size, color or some other configuration parameterassociated with previous resource transfer events. Since the userpreference data is stored by and retrieved from the resource storageentity, which in specific embodiments, is a financial institution or thelike, the user does not have to hold an account at the network site 76or otherwise store data, including the user preference data 54 at thenetwork site 76 level or at the browser level, which are highlysusceptible to data breaches or the like. The resource storage entity,such as a financial institution is a trusted entity and thecommunication links between the instructions 64 and the user database48, used for accessing and retrieving data therefrom, may be securedcommunication channels, such as tunnel connections or the like.

Referring to FIG. 3 a block diagram is depicted that illustratesexemplary resource transfer event messaging implemented in conjunctionwith a real-time processing network, in accordance with embodiments ofthe present invention. Real-time processing networks, includingreal-time payment networks are discussed in detail infra. with respectto FIGS. 4-7. In specific embodiments of the invention, the real-timeprocessing network 300 is configured to allow the second user/resourcerecipient 100B to generate and communicate a resource transfer eventrequest message 23, which allows for the user 100B to include a request25 for second user data 18 within the message 23. In specificembodiments of the invention, the request 25 for second user data 18, isa request for specific resource provider preference(s) 20, such as arequest for object/service configuration preferences (e.g., size, coloror the like), geographic location preference for delivery of anobject/product or performance of a service, a contact preference, suchas an email address, telephone number or the like.

The resource transfer event request message 23 is communicated to thefirst user/resource provider 100A via the real-time processing network300. In response, the real-time processing network is configured tofirst user/resource provider 110A to generate and communicate a resourcetransfer event message 22 that includes first user data 14 that isrequired to affect the resource transfer event, such as resourcetransfer event credentials 16, which may comprise an resource accountidentifier, token or the like. In addition, the resource transfer eventmessage 22 that includes second user 18, which includes responses to thespecific request 25, such as resource provider preferences 20. Thereal-time processing network 300 receives the resource transfer eventmessage 22 and processes the resource transfer event in real-time ornear-real time to receiving the message. Real-time processing means thatthe resource transfer occurs, e.g., resources are distributed andsettlement occurs between two or more resource storage entities, inreal-time.

In addition, the real-time processing network 300 is configured togenerate a second resource transfer event message that is communicatedto the second user/resource recipient 100B and includes the second userdata 18 which includes (i) responses to the specific request 25, such asresource provider preferences 20 and, in some embodiments, (ii) resourcetransfer event confirmation data 29 that confirms the resource transferevent. In this regard, the second user/resource recipient 100 b receivesresource transfer event confirmation 29 and requested second user data18 in one consolidated message 27 from the real-time processing network300. This serves two different technical benefits. First, by sendingconsolidated messages that include either (i) the resource transferevent request and the request for second user data, or (ii) the resourcetransfer event confirmation and requested second user data, iteliminates the need to communicate the request fir second user data andthe second user data itself in separate messages. By not having tocommunicate the request for second user data and the second user data inseparate messages, less burden is placed on the communication network(i.e., bandwidth used to communicate separate messages can be used forother purposes. Second, currently the requests for second user data andthe second user data is communicated from and to the seconduser/resource recipient 110 by means other than the real-time processingnetwork (i.e., text message, voice network or the like). Typically, suchother means are less secure and/or reliable than the real-timeprocessing network 300. Thus, the present invention also provides forheightened security and reliability in the communication of requests forsecond user data and the subsequent second user data.

In specific embodiments of the invention in which the resource transferevent is payment event and the real-time processing network is areal-time payment network, the messaging may be in accordance withInternational Organization of Standardization (ISO) 20022 standard forelectronic data interchange between financial institutions. In suchembodiments of the invention, PACO.13 (Party Contact Narrative) definesa postal address field and PAIN.008 (Payments Initiation) provides afield for a customer address. Additionally, ISO 20022 provides for anunstructured remittance in both the payment request and payment (i.e.,credit transfer) message. in specific embodiments of the invention, analphanumeric code may be employed in the unstructured remittance field,such that, one or more character/number positions in the codecorresponds to a different user preference datum (i.e., a differentsize, color or the like),

FIG. 4 illustrates a block diagram of a high-level real-time processingsystem 100, in accordance with embodiments of the present invention. Inthe illustrated system 100, a first user 110A is associated with a firstresource storage entity system 130 and a second user 110B is associatedwith a second resource storage entity system 140. A real-time processingnetwork 300 is configured to process, in real-time, a resource transferevent 310, in which first user 100 a is the resource provider and seconduser 100 b is the resource recipient. In specific embodiments of theinvention, real-time processing provides for the resources to beavailable to the resource recipient immediately (i.e., once thereal-time processing network 300 has completed processing the resourcetransfer event 310). In other embodiments of the invention, real-timeprocessing provides for the resource transfer event 310 to becleared/settled upon completion of processing by the real-timeprocessing network 300. In specific embodiments of the invention, thereal-time processing nature means that once the first user 100 ainitiates the resource transfer event 310, the resource transfer eventis deemed irrevocable (i.e., the resource transfer event cannot becancelled or otherwise prevented from completion).

In specific embodiments of the invention, the first user 110A and thesecond user 110B are users of the real-time processing system 100, suchthat, the first user 110A initiates a resource transfer event in whichthe second user 110B is the resource recipient. In specific embodimentsof the invention, the first user 110A initiates the resource transferevent from the first resource storage entity system 130 by providingrequisite authentication information, which serves to authenticate theidentity of the first user 110A. In specific embodiments of theinvention, authentication of an identity may includemulti-factor/multi-step authentication (i.e., involving one or morecomputing devices) as required by information security standards andrequirements. The first user 100A may also provide, as part of theauthentication information, a resource depository identifier, whichserves to identify a source for resources associated with the resourcetransfer event 310. In such embodiments of the invention, first resourcestorage entity system 130 may authenticate the validity of the resourcedepository and validate that the resource depository currently stores anadequate volume of resources to process the resource transfer event 310.

In specific embodiments of the invention, once the first user 100Ainitiates the resource transfer event 310, the second user 110B, as theresource recipient, receives communication, via the second resourcestorage entity system 140 to accept the resources (i.e., accept theresource transfer event) following performance of requisite userauthentication requirements. Communication between first user 100A andsecond user 100B related to the resource transfer event is transmittedbetween the first and second resource storage entity systems 130 and 140via the real-time processing network 300. The real-time processingnetwork 300 is configured to directs the resources to the appropriateresource storage entity system associated with resource recipient, inthis instance second resource storage entity system 140 associated withthe second user 100 b.

It should be understood that while the illustrated embodiment of FIG. 4depicts only first and second users 100A and 100B, and first and secondresource storage entity systems 130 and 140, in actual embodiments of areal-time processing network 300 numerous resource storage entitysystems having corresponding numerous users may interact with thereal-time processing network 300 to process, as needed, resourcetransfer events 310 in real-time.

In accordance with specific embodiments of the invention, the terms“resource storage entity system” may include any computing systemcomprising one or more computing devices (e.g., servers, storagedevices, personal computers (PCs) and the like) associated withentity/organization having a need to process resource transfer events inreal-time.

Furthermore, the term “user” may include a single individual or a groupof individuals that desire to perform a resource transfer event inreal-time. The “user”, as referenced herein, may refer to an individualor group of individuals that has the ability and/or authorization toaccess and use one or more resources or portions of a resource andrequest and initiate real-time processing via the real-time processingnetwork 300. Moreover, the association between the users and theresource storage entity systems may be a one-time association for thepurpose of processing the resource transfer event in real-time or theassociation may be an ongoing association in which the users regularlyprocess resource transfer events, those in real-time and otherwise, withthe associated resource storage entity system.

As used herein, the term “user computing device” or “mobile device” or“communication device” may refer to mobile phones, personal computingdevices, tablet computers, wearable devices, smart devices and/or anyportable electronic device capable of receiving (wirelessly orotherwise) and/or storing data therein. A “user interface” is any deviceor software that allows a user to input information, such as commands ordata, into a device, or that allows the device to output information tothe user. For example, the user interface may include a graphical userinterface (GUI) or an interface to input computer-executableinstructions that direct a processing device to carry out specificfunctions. The user interface typically employs certain input and outputdevices to input data received from a user second user or output data toa user. These input and output devices may include a display, mouse,keyboard, button, touchpad, touch screen, microphone, speaker, LED,light, joystick, switch, buzzer, bell, and/or other user input/outputdevice for communicating with one or more users.

A “system”, as used herein, may refer to any information technology (IT)platform and may include a plurality of computing devices, such asservers, mainframes, personal computers, network devices (portable andotherwise), front and back end devices, database/storage devices and/orthe like.

Referring to FIG. 5 a block diagram is depicted of a high-levelreal-time processing system 200, in accordance with one embodiment ofthe invention. In the illustrated embodiments, a first user 110A isassociated with a first resource storage entity system 130 and a seconduser 110B is associated with a second resource storage entity system140. The real-time processing network 300 is configured as a clearinghouse system in which the resource transfer event 310 is conductedbetween a first resource storage entity-specific resource depository 320and a second resource storage entity-specific resource depository 330.The first resource storage entity-specific resource depository 320 andthe second resource storage entity-specific resource depository 330 areaccessible by each respective resource storage entity system, i.e.,first resource storage entity-specific resource depository 320 isaccessible to first resource storage entity system 130 andsecond-entity-specific resource depository 330 is accessible to secondresource storage entity system 140. The real-time processing network 300acts as a trusted intermediary during completion (e.g.,clearing/settlement) of the resource transfer event 310. Resources arebe transferred by each resource storage entity system 130 and 140 to andfrom their respective entity-specific resource depositories 320 and 330.Resource transfers between the first user-specific resource depository132 and the second user-specific resource depository 142 areadministered by the clearing house system 300 pending authentication andauthorization of the users 110A and 100B and/or the user-specificresource depositories 132 and 142 as required by the resource transferevent 310.

The clearing house system of the real-time processing network 300 isconfigured to direct the resources to the appropriate resource storageentity system associated with the second user 100B (i.e., resourcerecipient). The transfer of resources occurs between the first resourcestorage entity-specific resource depository 320 and second resourcestorage entity-specific resource depository 330 on behalf of theirassociated users 110A and 110B, wherein the resource transfer event 310may be cleared/settled at the resource storage entity systemsimmediately, concurrent with the completion of the resource transferevent. As settlement occurs between the representative resource storageentity systems 130 and 140, resources are deleted from and added to thecorresponding user-specific resource depositories 132 and 142. As aresult of the resource transfer event being is settled immediately, theresources are made available for use by the resource recipient (e.g.,second user 100B) in real or near real-time.

In specific embodiments of the invention, the system 500 may furthercomprise more than one real-time processing network 300/clearing housesystem that receive and process resource transfer event requests asdescribed herein.

Referring to FIG. 6 a block diagram is shown of a high-level real-timeprocessing system 400, in accordance with embodiments of the presentinvention. In the illustrated system 100, a first user 110A isassociated with a first payment processing entity system 130, such as acustomer of a first financial institution and a second user 110B isassociated with a second payment processing entity system 140, such as acustomer of a second financial institution. In this regard the real-timeprocessing network 300 otherwise referred to as a real-time payment(RTP) network is configured to process, in real-time, a resourcetransfer event in the form of a transaction/disbursement 310 of funds,in which first user 100 a provides the funds and second user 100 breceives the funds. In specific embodiments of the invention, real-timepayment provides for the funds to be available to the recipient (i.e.,second user/customer 100B) immediately (i.e., once the real-time paymentnetwork 300 has completed processing the transaction/disbursement 310).In other embodiments of the invention, real-time payment provides forthe transaction/disbursement 310 to be cleared/settled upon completionof processing by the RTP network 300. In specific embodiments of theinvention, the real-time aspect of RTP network 300 means that once thefirst user 100A initiates the transaction/disbursement 310, thetransaction/disbursement 310 is deemed irrevocable (i.e., thetransaction/disbursement cannot be cancelled, interrupted or otherwiseprevented from completion/settlement) and the first user 100A bares anobligation to remit the funds to the second user 100B.

In specific embodiments of the invention, the RTP network 300 isconfigured to communicate in accordance with an industry-wide standardmessaging protocol. For example, in specific embodiments of theinvention, the messaging protocol may adhere to InternationalOrganization for Standardization (ISO) standard 20022, which detects theformat and rules for communicating messages/commands between the paymentprocessing entity systems 130 and 140 and the RTP network 300. Inspecific embodiments of the invention, the transaction/disbursement 310may occur, in its entirety, via a series of messages communicatedbetween the payment processing entities 130 and 140 via the RTP network300. While in other embodiments of the invention, such as those,discussed in relation to FIG. 7, infra., the RTP network 300 willimplement a clearing house system.

In specific embodiment of the invention, the first user 110A and thesecond user 110B are predetermined users (i.e., registered users) of thereal-time processing system 400, wherein the first user 110A (i.e., thepayor) initiates a credit transfer to the second user 110B (i.e., thepayee). In specific embodiments of the invention, the first user 110A isrequired to initiate the transfer from the first payment processingentity system 130 in response to the first user 110 a providingauthentication information to authenticate the identity of the firstuser 110A and validity of the first user account 132 held at the firstpayment processing entity system 130. The authentication information mayinclude account numbers, routing numbers, PIN numbers, username andpassword, date of birth, social security number, or the like, or otherauthentication information as described herein. As previously described,in some embodiments of the invention, user identity authentication maycomprise multi-factor/multi-step authentication as prescribed byinformation security standards and requirements. In addition, the system400 may provide for authorizing the transaction/disbursement 310 basedon verifying the first user account 132 held at the first paymentprocessing entity system 130 currently stores at least an adequateamount of available funds to fulfill the transfer/disbursement 310.While in certain embodiments of the invention, the first user 110 ainitiates the transfer from a physical, brick-and-mortar location of thefirst payment processing entity system 130, in alternative embodimentsdescribed herein, the transfer may be initiated from other locations inwhich the user is not required to be at a brick-and-mortar location(e.g., via an electronic application, a website, a point-of-sale (POS)device or the like).

Upon the first user 100A initiating transaction/disbursement 310, thesecond user 110B, as the payee, receives a communication to acceptpayment in response to the second user providing requisiteauthentication information and the system 400 verifying the identity ofthe second user and the validity of the second user account 142. Aspreviously discussed, communication related to thetransaction/disbursement 310 between first and second user 100A istransmitted between the first and second payment processing entitysystems 130 and 140 via the real-time processing network 300 whichdirects the payment to the appropriate payment processing entity (e.g.,second payment processing entity system 140) associated with the paymentrecipient (i.e., second user 100B). As settlement occurs between therepresentative first and second payment processing entity systems 130and 140, debiting and crediting of individual user accounts (i.e., firstand second user accounts 132 and 142) may be managed at each paymentprocessing entity system. As the transaction/disbursement is settledimmediately, funds may be made available for use by the recipient (i.e.,second user 100B) in real or near real-time.

The payment processing entity systems 130 and 140 may be associated withfinancial institutions or any other entity/organization that processesfinancial transactions/disbursements or the like. Additionally, itshould be appreciated by someone with ordinary skill in the art that theuser may be an existing customer of the financial institution or apotential customer of the financial institution or the like.

Referring to FIG. 7 a block diagram is depicted of a high-levelreal-time processing system 500, in accordance with one embodiment ofthe invention. In the illustrated embodiments, a first user 110A isassociated with a first payment processing entity system 130, such as acustomer of a first financial institution and a second user 110B isassociated with a second payment processing entity system 140, such as acustomer of a second financial institution. The real-time processingnetwork 300 is a real-time payment (RTP) network configured as aclearing house system in which the transaction/disbursement 310 isconducted between a first entity-specific account 330 and a secondentity-specific account 340. The first entity-specific account 330 andthe second entity-specific account 340 are accessible by each respectivepayment processing entity system, i.e., first entity-specific account330 is accessible to first entity/financial institution system 130 andsecond entity-specific account 340 is accessible to secondentity/financial institution system 140. The RTP network 300 acts as atrusted intermediary during settlement of the transaction/disbursement310. Funds are be transferred by each payment processing entity system130 and 140 to and from their respective entity-specific accounts 330and 340. Fund transfers between the first user account 132 and thesecond user account 142 are administered by the clearing house system300 pending authentication and authorization of the users 110A and 100Band/or the user accounts 132 and 142 as required by thetransaction/disbursement 310.

The clearing house system of the RTP network 300 is configured to directthe funds to the appropriate payment processing entity system/financialinstitution associated with the second user 100B (i.e., payee). Thetransfer of funds occurs between the first payment processing entityaccount 330 and second payment processing entity account 340 on behalfof their associated users 110A and 110B. As such, thetransaction/disbursement 310 may be cleared/settled at the paymentprocessing entity systems/financial institutions immediately, concurrentwith the completion of the transaction/disbursement. As settlementoccurs between the representative payment processing entitysystems/financial institutions 130 and 140, funds are debited andcredited to the corresponding user accounts 132 and 142. As a result ofthe transaction/disbursement being is settled immediately, the funds aremade available for use by the payee (e.g., second user 100B) in real ornear real-time.

In specific embodiments of the invention, the system 300 may furthercomprise more than one RTP network 300/clearing house system thatreceive and process transaction/disbursement requests as describedherein.

Referring to FIG. 8 a flow diagram is depicted of a method 400 forresource transfer event messaging, in accordance with embodiments of thepresent invention. At Event 410, inputs are received that define (i)first user data associated with a resource provider and required toaffect a resource transfer event between the resource provider and aresource recipient, and (ii) second user data associated with theresource recipient, such as user preference data. In specificembodiments of the method, in which the resource transfer event is apayment event, the first user data may be the payor's paymentcredentials (e.g., account identifier or the like). The user preferencedata may include, but is not limited to, object/service configurationpreference data (i.e., size, color and the like), geographic locationpreference data for delivering the object or performing the service,contact preference data (e.g., email address, telephone number or thelike). The inputs may be received from the user/resource provider, theresource storage entity, such as a financial institution, a web browseror a web site or the like.

At Event 420, a resource transfer event message is generated thatincludes (i) the first user data and (ii) the second user data. Inspecific embodiments of the invention in which the resource transferevent is a payment event, the resource transfer event message may be apayment/credit transfer message or the like. At Event 430, the resourcetransfer event message is communicated to resource storage entityassociated with the first user. In specific embodiments of the inventionin which the resource transfer event is a payment event, the resourcetransfer event message is communicated to a payment processing entity,such as a financial institution at which the payor holds the paymentaccount.

At Event 440, the resource storage entity validates the resourcetransfer event based on the first user data. In specific embodiments ofthe invention in which the resource transfer event is a payment event,the payment processing entity validates the payment transaction byverifying the payment credentials and, in some instances, amount ofresources/funds in the payment account.

At Event 450, a user record is stored at or by the resource storageentity that includes resource transfer event data and the second userdata. The user record serves to associate the resource provider with theresource transfer event and the second user data.

In further embodiments of the method, in response to validating theresource transfer event, a second resource transfer event message isgenerated and communicated to the resource recipient that includes, butis not limited to, the second user data. In such embodiments the method,the resource recipient may not receive any other messages associatedwith the resource transfer event. In specific embodiments of theinvention in which the resource transfer event is a payment event, thesecond resource transfer event message is a payment confirmation messagecommunicated to the resource recipient that includes payment amount andthe second user data, such as user preference data (e.g.,product/service configuration preference data, physical addresspreference for delivering the product or performing the service, contactpreference or the like).

In other specific embodiments of the method, the messaging may beimplemented as part of a real-time processing network. In suchembodiments of the invention, a resource transfer event request messagemay be initiated by the resource recipient and communicated to theresource provider. In such embodiments of the method, the resourcetransfer event request message is configured to allow for the resourcerecipient to input requests for second user data therein. In suchembodiments of the method, the request message precedes receiving theinputs of the first and second user data and generating andcommunicating the resource event transfer message. In those embodimentsof the method in which the resource transfer event is a payment event,the resource transfer event request message may be payment requestmessage communicated from the payment requester/recipient/payee to thepayment provider/payor.

Referring to FIG. 9 a flow diagram is depicted of a method 500 forleveraging user preference data communicated in resource transfer eventmessages to customize/personalize a user experience during web browsing,in accordance with embodiments of the present invention. At Event 510,user data is stored for a plurality of users. The user data associateseach of the users with user preference data that has been received viaresource transfer event messages communicated to a resource storageentity during resource transfer events. The user preference dataincludes object/server configuration preference data. In specificembodiments of the invention in which the resource transfer event is apayment event, the user preference data has been received via paymentmessages communicated to the payment processing entity as part of thepayment event.

At Event 520, user authentication credentials are received from one ofthe users and, at Event 530, the user is authenticated by matching thereceived user authentication credentials with the user authenticationstored at the resource storage entity. For example, specific embodimentsof the invention in which the resource transfer event is a paymentevent, the user may authenticate with the payment processing entity,such as a financial institution or the like via a designated portal orvia a widget implemented in conjunction with a web browser.

In response to authenticating the user, at Event 540, the user accessesa network configured for initiating resource transfer events. Forexample, specific embodiments of the invention in which the resourcetransfer event is a payment event, the user accesses the Internet. AtEvent 550, in response to the user navigating to a network site in thenetwork, the stored user data is accessed and the user preference dataassociated with the user is retrieved.

At Event 560, content provided to the user while browsing the networksite is customized/personalized based on the user preference data,specifically, the object/service configuration preference data. Forexample, if the object/service preference data indicates that the userprefers specific items of a specific size (e.g., shoes in size 10), theweb site may be configured to only show the specific items offeredand/or currently available in the specific size without the userotherwise having to make an input that notifies the website of theirpreferred size. As previously discussed, since the user preference datais stored at the resource storage entity-level, such as a paymentprocessing entity-level, the data is deemed to be more securely andconfidentially held than would be afforded if the data was stored eitherat the web browser-level or at the network site-level.

In other embodiments of the method, the user preference data includes afor delivery of the object or performance of the service, a contactpreference (e.g., email address, telephone number or the like) forcorresponding with the resource provider and the like. In relatedembodiments the method may further include the user/resource providing asingle input at the network site for acquisition of an object/product orperformance of a service. In such embodiments of the method, in responseto receiving the single input or prior to the single input, the resourcestorage entity is accessed to obtain the resource transfer eventcredentials, such as, as payment credentials associated with theuser/resource provider and the user database is accessed to obtain theuser preference data including, but not limited to, user configurationpreference data, such as preferences (e.g., sizes, colors and the like)for the object or service being acquired, a geographic locationpreference for delivery of the object or performance of the service, acontact preference (e.g., email address, telephone number or the like)for corresponding with the resource provider and the like. In response,the resource transfer event is processed using only the resourcetransfer event credentials and the user preference data obtained fromthe resource storage entity and user database. In those embodiments ofthe invention in which the resource storage event is a payment event,the user provides a single input and all of the information needed toprocess the payment event (i.e., payment credentials, delivery address,product configuration info and contact information) is obtained from thepayment processing entity. In addition to the user benefitting from anactual “one input” (i.e., single click) transaction, the informationthat is used to process the transaction is stored and retrieved from atrusted entity (i.e., the payment processing entity, such as a financialinstitution or the like) and, thus, the user is not required to storethe information at the less secure web browser and/or web site level.

In specific embodiments of the method, the resource transfer eventmessages that include the user preference data implicate a real-timeprocessing network. In those embodiments of the invention in which theresource storage event is a payment event, the resource transfer eventmessage is payment/credit transfer message. In such embodiments of themethod, communication of the resource transfer event message may bepreceded by a resource transfer event request message. In thoseembodiments of the invention in which the resource storage event is apayment event, the resource transfer event request message is paymentrequest message. In such embodiments of the invention, the resourcetransfer event request message may be configured to allow the user toconfigure the message with specific user preference data request, suchas requests for product configuration preferences, delivery address orservice performance address, contact preference or the like.

In further specific embodiments of the method, once the preference datais accessed, logic may be implemented, such as artificial intelligenceor the like, to determine actual user preferences applicable to thenetwork site. For example, the network site may be specific to aparticular brand of products and the stored user preference data may beassociated with one or more different brands of products. In suchinstances, the logic may be implemented to determine the user preference(e.g., size) to the brand offered at the network site based on thestored user preference data associated with the other brands. Forexample, the user preference data may indicate that the user has apreference for size 9 shoes of brand XYZ, however the logic maydetermine that in brand ABC offered at the network site, the user'sactual preference is for size 9½ shoes.

Thus, present embodiments of the invention provide for systems,apparatus methods and/or the like for configuring resource transferevent messages to include, not only the user data required to affect theresource transfer (e.g., resource repository identifier and the like),but other user data related to the resource transfer event, such as userpreference data and the like. The resource transfer event messages arecommunicated to resource storage entities that subsequently store userrecords that associate users with the resource transfer events and theadditional user data. In this regard, the resource storage entities canleverage the additional data to investigate potential nefarious actions,confirm resource storage event preferences/specifics and the like.Moreover, the present invention, in specific embodiments lessens thevolume of resource transfer event messages or other network-basedmessages thereby limiting network traffic and making the overall processmore efficient and effective.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible.

Those skilled in the art may appreciate that various adaptations andmodifications of the just described embodiments can be configuredwithout departing from the scope and spirit of the invention. Therefore,it is to be understood that, within the scope of the appended claims,the invention may be practiced other than as specifically describedherein.

1. A system for resource transfer event messaging, the systemcomprising: a first computing platform including a first memory and atleast one first processor in communication with the first memory,wherein the first memory stores first instructions that are executableby the at least one first processor, implemented in conjunction with areal-time processing network configured to complete processing of theresource transfer in real-time and configured to: receive inputs thatdefine (i) first user data associated with a resource provider andrequired to affect a resource transfer event conducted between theresource provider and a resource recipient, and (ii) second user dataassociated with the resource provider, wherein the second user data isdata other than the first user data, generate a real-time processingresource transfer event message in accordance with InternationalOrganization of Standardization (ISO) 20022 and including (i) the firstuser data, and (ii) the second user data, and communicate the real-timeprocessing resource transfer event message to a resource storage entityassociated with the resource provider; and a second computing platformincluding a second memory and at least one second processor incommunication with the second memory, wherein the second memory storessecond instructions that are executable by the at least one secondprocessor and configured to: receive, at the resource storage entity,the real-time processing resource transfer event message, validate theresource transfer event based on the first user data, and store a userrecord that associates the resource provider with the resource transferevent and the second user data.
 2. The system of claim 1, wherein thesecond instructions are further configured to: in response to validatingthe real-time processing resource transfer event, generate a secondreal-time processing resource transfer event message including thesecond user data and less than an entirety of the first user data, andcommunicate the second real-time processing resource transfer eventmessage to the resource recipient.
 3. The system of claim 1, wherein thesecond user data includes user preference data comprising at least oneselected from the group consisting of (i) an object or servicepreference, (ii) a physical location preference for conveying the objector performing the service, and (iii) a contact preference forcommunicating with the resource provider.
 4. The system of claim 1,wherein the first instructions configured to receive the inputs arefurther configured to receive the inputs from one of (i) the resourcerecipient, or (ii) the resource storage entity.
 5. (canceled)
 6. Thesystem of claim 1, wherein the first instructions configured to generatethe real-time processing resource transfer event message are furtherconfigured to provide the second user data as an alpha numeric codewithin a designated field of the real-time processing resource transferevent message, wherein predetermined characters in the alphanumeric codecorrespond to different second user datum.
 7. The system of claim 1wherein the first instructions are further configured to generate aresource transfer event request message that is communicated to theresource provider and is configured to request (i) the resource transferevent and (ii) the second user data, and wherein the first instructionsconfigured to receive the inputs are further configured to receive theinputs from the resource provider in response to receiving the resourcetransfer event request message.
 8. The system of claim 7, wherein thefirst instructions configured to generate the resource transfer eventrequest message are further configured to receive inputs from theresource recipient that define the second user data that is beingrequested.
 9. The system of claim 7, wherein the first instructionsconfigured to generate the resource transfer event request message arefurther configured to include the request for the second user data as analphanumeric code in an unstructured remittance field of the resourcetransfer event request message, wherein predetermined characters in thealphanumeric code correspond to different requests for second userdatum.
 10. A computer-implemented method for resource transfer eventmessaging implemented in conjunction with a real-time processing networkconfigured to complete processing of a resource transfer event inreal-time, the method executed by one or more computing processordevices and comprising: receiving inputs that define (i) first user dataassociated with a resource provider and required to affect the resourcetransfer event conducted between the resource provider and a resourcerecipient, and (ii) second user data associated with the resourceprovider, wherein the second user data is data other than the first userdata; generating a real-time processing resource transfer event messagein accordance with International Organization of Standardization (ISO)20022 and including (i) the first user data, and (ii) the second userdata; communicating the real-time processing resource transfer eventmessage to a resource storage entity associated with the resourceprovider; validating, at the resource storage entity, the resourcetransfer event based on the first user data; and storing a user recordthat associates the resource provider with the resource transfer eventand the second user data.
 11. The computer-implemented method of claim10, further comprising: in response to validating the real-timeprocessing resource transfer event message, generating a secondreal-time processing resource transfer event message including thesecond user data and less than an entirety of the first user data; andcommunicating the real-time processing second resource transfer eventmessage to the resource recipient.
 12. The computer-implemented methodof claim 10, wherein the second user data includes user preference datacomprising at least one selected from the group consisting of (i) anobject or service preference, (ii) a physical location preference forconveying the object or performing the service, and (iii) a contactpreference for communicating with the resource provider.
 13. Thecomputer-implemented method of claim 10, receiving the inputs furthercomprises receiving the inputs from one of (i) the resource recipient,or (ii) the resource storage entity.
 14. (canceled)
 15. Thecomputer-implemented method of claim 10, further comprising: generatinga real-time processing resource transfer event request message that iscommunicated to the resource provider and is configured to request (i)the resource transfer event and (ii) the second user data.
 16. Acomputer program product comprising: a non-transitory computer-readablemedium comprising: a first set of codes for causing a computer toreceive inputs that define (i) first user data associated with aresource provider and required to affect a resource transfer eventconducted between the resource provider and a resource recipient, and(ii) second user data associated with the resource provider, wherein thesecond user data is data other than the first user data; a second set ofcodes for causing a computer to generate real-time processing resourcetransfer event message in accordance with International Organization ofStandardization (ISO) 20022 and including (i) the first user data, and(ii) the second user data; a third set of codes for causing a computerto communicate the real-time processing resource transfer event messageto a resource storage entity associated with the resource provider; afourth set of codes for causing a computer to validate, at the resourcestorage entity, the resource transfer event based on the first userdata; and a fifth set of codes for causing a computer to store a userrecord that associates the resource provider with the resource transferevent and the second user data wherein the sets of codes are implementedin implemented in conjunction with a real-time processing networkconfigured to complete processing of the resource transfer in real-time.17. The computer program product of claim 16, further comprising: asixth set of codes for causing a computer to, in response to validatingthe real-time processing resource transfer event message, generate asecond real-time processing resource transfer event message includingthe second user data and less than an entirety of the first user data;and a seventh set of codes for causing a computer to communicate thesecond real-time processing resource transfer event message to theresource recipient.
 18. The computer program product of claim 16,wherein the second user data includes user preference data comprising atleast one selected from the group consisting of (i) an object or servicepreference, (ii) a physical location preference for conveying the objector performing the service, and (iii) a contact preference forcommunicating with the resource provider.
 19. (canceled)
 20. Thecomputer program product of claim 16, further comprising: a sixth set ofcodes for causing a computer to generate a resource transfer eventrequest message that is communicated to the resource provider and isconfigured to request (i) the resource transfer event and (ii) thesecond user data.